home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
TeX 1995 July
/
TeX CD-ROM July 1995 (Disc 1)(Walnut Creek)(1995).ISO
/
tex-k
/
tex-k-archive.past
/
1995.02
/
000111_bob@gnu.ai.mit.edu_Thu Feb 16 13:14:29 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-02-28
|
3KB
Received: from albert.gnu.ai.mit.edu by cs.umb.edu with SMTP id AA15998
(5.65c/IDA-1.4.4 for <tex-k@cs.umb.edu>); Thu, 16 Feb 1995 18:14:38 -0500
Received: from hill.gnu.ai.mit.edu by albert.gnu.ai.mit.edu (5.65/4.0) with SMTP
id <AA06703@albert.gnu.ai.mit.edu>; Thu, 16 Feb 95 18:14:32 -0500
Received: by hill.gnu.ai.mit.edu (15.11/4.0)
id <AA28101@hill.gnu.ai.mit.edu>; Thu, 16 Feb 95 18:14:29 est
Date: Thu, 16 Feb 95 18:14:29 est
From: bob@gnu.ai.mit.edu
Message-Id: <9502162314.AA28101@hill.gnu.ai.mit.edu>
To: swift@bu.edu
Cc: tex-k@cs.umb.edu, bob@gnu.ai.mit.edu
In-Reply-To: <199502162120.QAA270264@acs3.bu.edu> (swift@acs.bu.edu)
Subject: Re: m68k-sony-newsos build
swift@acs.bu.edu says, rightly,
... it is very reasonable to say that one would like to be able to
process the example files like simple.tex, ... building
fonts ... the latex format, the latex fonts ...
... and I would add Texinfo, which what I use.
I think *all* these are part of the vanilla TeX. Hey, remember, I
wanted to know how much disk space is required? :-)
A plain top level `make' should make `all' unless you tell it
otherwise. (Actually, by `all' I don't mean absolutely all--I know
that TeX has a lot, but I do mean the major subpackages that come to
mind when someone asks you. This is alot, and I would not recommend
this except the price of disk space is falling.)
The README file should have a little table somewhat like this:
What you type: What you get: How much disk space you need:
------------- ------------ ----------------------------
make every std thing nnn Megabytes
(with list here
or in footnote)
make latex Latex and some mm megabytes
commonly assoc.
features
Maybe a fourth column should warn how many hours of build time is
required on various types of machine? :-)
These expectations, however, assume a source tar.gz file that
is _entirely_ self-sufficent ...
No, that is not the case. It assumes a visible, top level readme file
that tells me what tar.gz files I need for the from-scratch,
`standard-all' installation. The bunch of source files that together
are self-sufficient. That same readme file could tell me what the
other options are, how much space they require, which tar.gz files
they take.
Clearly, more complex updates and installations will need more
information than just what you can pack into a brief message and a
short table. But the top level readme could have pointers to
documents for that. This would be for the people who know what they
are doing, in contrast to the likes of me, who don't.
Robert J. Chassell bob@gnu.ai.mit.edu
25 Rattlesnake Mountain Road bob@grackle.stockbridge.ma.us
Stockbridge, MA 01262-0693 USA (413) 298-4725